I18N: Remove canonical/hreflang tags, let RTD handle SEO/locale negotiation #10209
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This was originally added as a stopgap (by me) and turned out to be less than satisfactory. In the mean time, RTD now generates sitemaps to handle this (compare https://docs.godotengine.org/sitemap.xml), and Google actually considers our generated links here broken due to no proper backlinks if you check via their Webmaster tooling.
Removing this should hopefully mean Google uses the Sitemap and the
<html lang="">tag to find links between alternate language versions, and prefer to show users the pages meant for their configured preferences for language/locale.If that turns out not enough, we need to revisit this, but fix the implementation to provide proper backlinks for all languages.